[dev-v2.10] rancher-logging 105.2.1-rc.1+up4.10.0 update #5115
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Meza <meza-xyz@proton.me>
Signed-off-by: Meza <meza-xyz@proton.me>
Signed-off-by: Meza <meza-xyz@proton.me>
Validation steps
Ex:-
longhorn-controller:
repository: rancher/hardened-sriov-cni
tag: v2.6.3-build20230913
|
Validation steps
Ex:-
longhorn-controller:
repository: rancher/hardened-sriov-cni
tag: v2.6.3-build20230913
|
|
Hey @jmeza-xyz - sorry for the extra headache here, but our team has just migrated logging charts primary source from this repo into https://github.com/rancher/ob-team-charts. As such it would be best if you create a PR in that repo for logging chart and then our team (O&B) can more easily incorporate this fix into the next release we sync into Note that this is still early into the migration and that while we migrated the source - and @adamkpickering fixed a bug in the process, we still haven't created the PR to make this the effective source |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Checkpoints for Chart Bumps
release.yaml:Chart.yaml and index.yaml:index.yamlfile has an entry for your new chart version.index.yamlentries for each chart matches theChart.yamlfor each chart.Fill the following only if required by your manager.
Issue:
rancher/rancher#49048 && SURE-9662
Solution
Added priorityClassName to DS resources for k3s/rke/rk2 only if value is populated in values.yaml
{{- with .Values.priorityClassName }} priorityClassName: {{ . }} {{- end }}Added podPriorityClassName in Logging/FluentBitAgent generic templates with the option to set it in the global or fluentd/fluentbit keys.
{{- with (default .Values.priorityClassName .Values.fluentd.podPriorityClassName) }} podPriorityClassName: {{ . }} {{- end }} {{- with (default .Values.priorityClassName .Values.fluentd.podPriorityClassName) }} podPriorityClassName: {{ . }} {{- end }}QA Testing Considerations
Example values.yaml used for testing. Comment out the
podPriorityClassNameto testpriorityClassName: global-level-testis passed down to all resources.additionalLoggingSources: rke2: enabled: true debug: true fluentbit: podPriorityClassName: resource-level-test resources: limits: memory: 512Mi requests: cpu: 20m memory: 512Mi fluentd: replicas: 1 podPriorityClassName: resource-level-test resources: limits: memory: 512Mi requests: cpu: 20m memory: 512Mi priorityClassName: global-level-test global: seLinux: enabled: true